String keys and Symbol keys mixed up, leading to invalid schema merge #198
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During #196, I found string and symbols are mixed up.
String keys come from the base file (
YAML.safe_load(File.read(@path))
) and Symbol keys come from the generate specs.Since String != Symbol, merge is buggy, as seen in c941c62
This PR symbolizes all keys during processing.
Keys are transformed to String back when dumping into YAML file.